Data share system, data process apparatus, and computer-readable recording medium

ABSTRACT

A data process apparatus for sharing shared data among plural data process apparatuses participating in an event. The data process apparatus includes a participation notification reception unit configured to receive a participation notification from each of the plural data process apparatus including first and second data process apparatuses in the event, a notifying unit configured to notify the second data process apparatus to the first data process apparatus as a data obtain target from which the shared data is to be obtained. The second data process apparatus is a data process apparatus from which the participation notification has already been received by the participation notification reception unit.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a data share system, a data processapparatus, and a computer-readable recording medium. For example, a datashare system, a data process apparatus, and a computer-readablerecording medium for sharing data between data process apparatuseshaving a communication function.

2. Description of the Related Art

For example, Japanese Laid-Open Patent Publication No. 2006-268626discloses a technology applied to a case of organizing a conferenceusing shared documents in which an organizer of the conference transmitsdocuments to be shared by transmitting document data to terminals(clients) of the participants of the conference from a server prior tothe conference.

Thus, the sharing of data by transmitting/receiving data between aserver and a client is known.

However, with the conventional method, data is shared between dataprocess apparatus by providing shared data from a single data processapparatus to other data process apparatuses. This results to problems ofa large work load and a long data transmission time.

For example, in a case where of a conference having many participants,multiple data process apparatuses need to obtain data of documents usedin the conference by accessing a data process apparatus providing shareddata before the conference. Therefore, access for obtaining shared datais concentrated to the data process apparatus that provides the shareddata. This results in large communication process load and a long timefor transmitting the shared data. Thus, in a case of sharing databetween multiple data process apparatuses, it is desired to reduceprocess load by dispersing the process load and to share dataefficiently.

SUMMARY OF THE INVENTION

The present invention may provide a data share system, a data processapparatus, and a computer-readable recording medium that substantiallyobviate one or more of the problems caused by the limitations anddisadvantages of the related art.

Features and advantages of the present invention are set forth in thedescription which follows, and in part will become apparent from thedescription and the accompanying drawings, or may be learned by practiceof the invention according to the teachings provided in the description.Objects as well as other features and advantages of the presentinvention will be realized and attained by a data share system, a dataprocess apparatus, and a computer-readable recording medium particularlypointed out in the specification in such full, clear, concise, and exactterms as to enable a person having ordinary skill in the art to practicethe invention.

To achieve these and other advantages and in accordance with the purposeof the invention, as embodied and broadly described herein, anembodiment of the present invention provides a data process apparatusfor sharing shared data among plural data process apparatusesparticipating in an event, the data process apparatus including: aparticipation notification reception unit configured to receive aparticipation notification from each of the plural data processapparatus including first and second data process apparatuses in theevent; and a notifying unit configured to notify the second data processapparatus to the first data process apparatus as a data obtain targetfrom which the shared data is to be obtained; wherein the second dataprocess apparatus is a data process apparatus from which theparticipation notification has already been received by theparticipation notification reception unit.

Other objects, features and advantages of the present invention willbecome more apparent from the following detailed description when readin conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B are schematic diagrams for describing a configuration ofa data share system according to an embodiment of the present invention;

FIG. 2 is a schematic diagram illustrating an example of a hardwareconfiguration of a data process apparatus according to an embodiment ofthe present invention;

FIG. 3 is a schematic diagram illustrating a configuration of a datashare system providing a data share function according to an embodimentof the present invention;

FIG. 4 is a schematic diagram illustrating an example of a dataconfiguration of a participant list according to an embodiment of thepresent invention;

FIG. 5 is a schematic diagram illustrating an example of a dataconfiguration of an ongoing transmission list according to an embodimentof the present invention;

FIG. 6 is a schematic diagram illustrating an example of a dataconfiguration of a transmission completion list according to anembodiment of the present invention;

FIG. 7 is a sequence diagram illustrating steps in a case of performinga data sharing process (part 1) according to an embodiment of thepresent invention;

FIGS. 8A-8D are schematic diagrams illustrating transition of data of aparticipant list, a ongoing transmission list, a transmission completionlist in a case of performing a data sharing process (part 1) accordingto an embodiment of the present invention;

FIG. 9 is a schematic diagram illustrating operations performed in adata sharing operation (part 1) according to an embodiment of thepresent invention;

FIG. 10 is a sequence diagram illustrating steps performed in a case ofperforming a data sharing process (part 2) according to an embodiment ofthe present invention;

FIGS. 11A-11D are schematic diagrams illustrating transition of data ofa participant list, an ongoing transmission list, a transmissioncompletion list in a case of performing a data sharing process (part 2)according to an embodiment of the present invention;

FIG. 12 is a schematic diagram illustrating operations performed in adata sharing operation (part 2) according to an embodiment of thepresent invention;

FIG. 13 is a flowchart illustrating an example of a process ofdetermining a data obtain target according to an embodiment of thepresent invention;

FIGS. 14A and 14B are schematic diagrams illustrating operationsperformed in a data sharing operation (part 3) according to anembodiment of the present invention;

FIGS. 15A-15B are schematic diagrams illustrating operations performedin a data sharing operation (part 4) according to an embodiment of thepresent invention;

FIGS. 16A-16B are schematic diagrams illustrating operations performedin a data sharing operation (part 5) according to an embodiment of thepresent invention;

FIGS. 17A and 17B are schematic diagrams illustrating a data sharesystem according to a first modified example;

FIG. 18 is a schematic diagram illustrating an example of a hardwareconfiguration of a projection apparatus according to a first modifiedexample;

FIGS. 19A and 19B are schematic diagrams illustrating a data sharesystem according to a second modified example;

FIG. 20 is a schematic diagram illustrating a data share systemaccording to a third modified example; and

FIG. 21 is a schematic diagram illustrating a case where a data sharesystem of a third modified example is used for a conference.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS <System Configuration>

FIGS. 1A and 1B are schematic diagrams for describing a configuration ofa data share system 1000 according to an embodiment of the presentinvention. FIG. 1A illustrates a configuration having multiple dataprocess apparatuses 100 a-100 n (hereinafter also collectively referredto as “data process apparatus”) connected by a data transmission path N(e.g., a Local Area Network (LAN)). In this embodiment, the data sharesystem 1000 is applied to a wireless communication network. The datatransmission path N may be, for example, a wireless LAN or a Bluetooth(Registered Trademark) network.

The data process apparatus 100 includes, for example, a wirelesscommunication function, a data input function, and a data displayfunction. Although in this embodiment, the data process apparatus 100may include a desktop type personal computer (PC), the data processapparatus 100 is preferably a data terminal that is portable such as asmart phone or a tablet type PC.

FIG. 1B illustrates an example where the data share system 1000according to an embodiment of the present invention is used, for aconference. The data share system 1000 is used as follows. It is to benoted that the document data shared by data process apparatuses 100₁-100 ₄ in the conference is retained (stored) in the data processapparatus 100 ₁. The data process apparatus 100 includes a function ofallowing a screen (based on shared data) to be shared among the dataprocess apparatuses 100 ₁-100 ₄.

First, the organizer of the conference uses the data process apparatus100 ₁ to detect an access point AP located in a conference room of theconference and connect to a network. Thereby, the data process apparatus100 ₁ waits for other data process apparatuses 100 ₂-100 ₄ to transmit(send) a participation notification to the data process apparatus 100 ₁.

Then, in the state where the data process apparatus 100 ₁ is waiting, aparticipant A uses the data process apparatus 100 ₂ to detect the accesspoint AP and connect to the network. Thereby, the data process apparatus100 ₂ transmits a participation notification to the data processapparatus 100 ₁ to notify participation to the conference. In responseto the participation notification, the data process apparatus 100 ₁notifies device data of the data process apparatus 100 ₁ (i.e. devicedata pertaining to the data process apparatus 100 ₁ itself (self devicedata)) to the data process apparatus 100 ₂. Then, the data processapparatus 100 ₂ obtains the document data from the data processapparatus 100 ₁ based on the self device data notified from the dataprocess apparatus 100 ₁ and shares a conference document included in thedocument data.

Then, another participant B uses the data process apparatus 100 ₃ todetect the access point AP and connect to the network. Thereby, the dataprocess apparatus 100 ₃ transmits a participation notification to thedata process apparatus 100 ₁ to notify participation to the conference.In response to the participation notification, the data processapparatus 100 ₁ notifies device data pertaining to the data processapparatus 100 ₂ that is already sharing the document data (document dataobtained device) to the data process apparatus 100 ₃. Then, the dataprocess apparatus 100 ₃ obtains the document data from the data processapparatus 100 ₂ based on the device data notified from the data processapparatus 100 ₁ and shares the conference document included in thedocument data.

Then, another participant C uses the data process apparatus 100 ₄ todetect the access point AP and connect to the network. Thereby, the dataprocess apparatus 100 ₄ transmits a participation notification to thedata process apparatus 100 ₁ to notify participation to the conference.In response to the participation notification, the data processapparatus 100 ₁ notifies device data pertaining to the data processapparatus 100 ₃ that is already sharing the document data (document dataobtained device) to the data process apparatus 100 ₄. Then, the dataprocess apparatus 100 ₄ obtains the document data from the data processapparatus 100 ₃ based on the device data notified from the data processapparatus 100 ₁ and shares the conference document included in thedocument data.

Hence, with the data share system 1000 according to the above-describedembodiment, any one of the data process apparatuses 100 retaining shareddata can be an origin for providing the shared data to a newlyparticipating data process apparatus 100.

Accordingly, the data share system 1000 having the above-describedconfiguration can provide a distributed type data share service amongmultiple data process apparatuses 100.

The above-described access point (AP) may have a routing function (relayfunction) that relays data communications between an external network(public area) such as the Internet and an internal network (privatearea) such as LAN. In a case where the access point (AP) has suchrouting function, the data share system 1000 can provide a data shareservice in a wide area.

<Hardware Configuration>

FIG. 2 is a schematic diagram illustrating an example of a hardwareconfiguration of the data process apparatus 100 according to anembodiment of the present invention. As illustrated in FIG. 2, the dataprocess apparatus 100 includes, for example, an input device 101, adisplay device 102, a drive device 103, a RAM (Random Access Memory)104, a ROM (Read Only Memory) 105, a CPU (Central Processing Unit) 106,an interface device 107, and a HDD (Hard Disk Drive) 108 that areconnected to each other by a bus B.

The input device 101 includes, for example, a touch panel. The inputdevice 101 is used for inputting various operation signals to the dataprocess apparatus 100. The display device 102 includes, for example, adisplay. The display device 102 displays results of various processes(process results) performed by the data process apparatus 100.

The interface device 107 includes, for example, an interface thatconnects the data process apparatus 100 to the data transmission path N.Accordingly, the data process apparatus 100 can perform datacommunications with other data process apparatuses 100 by way of theinterface device 107.

The HDD 108 includes, for example, a non-volatile storage device thatstores various programs and data. The programs and data stored in theHDD 108 may include basic software (operating system (OS)) of a dataprocess system for control all of the data process apparatuses such asWindows (registered trademark) or UNIX (registered trademark). Theprograms and data stored in the HDD 108 may also include applicationsthat provide various functions in a system such as an application forexecuting a data share function. Further, the HDD 108 manages the storedprograms and data by using a predetermined file system and/or a database(DB).

The drive device 103 includes, for example, an interface between thedata process apparatus 100 and a removable recording medium(computer-readable recording medium) 103 a. Accordingly, the dataprocess apparatus 100 reads data from the recording medium 103 a and/orwrites data to the recording medium 103 a by way of the drive device103. The recording medium 103 a includes, for example, an SD (SecureDigital) memory card or a USB (Universal Serial Bus) memory.

The ROM 105 includes, for example, a non-volatile semiconductor memory(storage device) that can retain (store) internal data therein evenafter the power of the data process apparatus 100 is turned off. The ROM105 stores programs and data used for executing BIOS (Basic Input/OutputSystem) upon activation of the data process apparatus 100, setting up adata process system, and setting up a network. The RAM 104 includes, forexample, a volatile semiconductor memory (storage device) that cantemporarily retain (store) data and programs therein. The CPU 106includes, for example, a processor that controls the entire data processapparatus 100 and executes functions of the data process apparatus 100by obtaining data and programs from, for example, the HDD 108 or the ROM105 and loading the data and programs to the RAM (memory) 104, andexecuting various processes.

With the above-described data process apparatus 100 having theabove-described hardware configuration, various data process servicescan be provided.

<Data Share Function>

Next, a data share function according to an embodiment of the presentinvention is described.

For example, in a case where one of the data process apparatuses 100 (inthis example, also referred to as “organizer device”) is used by anorganizer organizing an event, the organizer device receives aparticipation notification(s) indicating participation to the event fromone or more other data process apparatuses 100 (in this example, alsoreferred to as “participation requesting device”). The organizer devicerefers to the data share status and the data transmission status of oneor more data process apparatuses (in this example, also referred to as“participating device”) whose participation notification(s) has alreadybeen received by the organizer device. The organizer device determines adevice (data obtain target) from which shared data is to be obtained bythe participation requesting device. Then, the organizer device notifiesdata of the data obtain target to the participation requesting device.Accordingly, the participation requesting device obtains the shared datafrom the data obtain target. Thereby, the data share function can beprovided by the data process apparatus 100 according to theabove-described embodiment of the present invention.

In a case where data share is performed among multiple data processapparatus according to a related art example, shared data is providedfrom a single data process apparatus (server) to other data processapparatus (clients). This results in a problem of large load and longdata transmission time. Thus, it is desired to efficiently share dataand reduce the workload of sharing data by distributing the workload.

With the data process apparatus 100 according to an embodiment of thepresent invention, in a case where the organizer device receives aparticipation request from the participation requesting device, theorganizer device notifies data of the participating device as data ofthe data obtain target and allows the participation requesting device toobtained shared data from the data obtain target.

Accordingly, the data share system 1000 including the data processapparatuses 100 provides an environment where the workload for obtainingshared data is distributed among the data process apparatuses 100. As aresult, the data share system 1000 can efficiently perform data andreduce the workload of sharing data.

Next, a configuration of the data share system 1000 and operation forproviding the data share function according to an embodiment of thepresent invention is described in further detail.

FIG. 3 is a schematic diagram illustrating a configuration of the datashare system 1000 providing the data share function according to anembodiment of the present invention. In FIG. 3, reference numeral 100 arepresents the organizer device (i.e. data process apparatus 100 of anorganizer organizing (holding) an event), reference numeral 100 brepresents the participating device (i.e. data process apparatus 100 ofa participant already participating in the event), and reference numeral100 c represents the participation requesting device (i.e. data processapparatus 100 of a participant requesting participation to the event).

As illustrated in FIG. 3, the data process apparatuses 100 a, 100 b, 100c include a communication control unit 11. The communication controlunit 11 includes, for example, various function units for controllingdata communication (reception/transmission of data (signals)) among thedata process apparatuses 100 a, 100 b, and 100 c. The function units ofthe communication control unit 11 include a participation notificationunit 111, a participation receive unit 112, a data obtain targetnotification unit 113, a data obtain unit 114, a data transmission unit115, and a transmission completion receive unit 116. The data sharefunction provided by the data process apparatuses 100 a-100 c of thedata share system 1000 is executed by cooperatively operating thefunction units of the communication control units 11 in the data processapparatuses 100 a-100 c.

In this example, mainly the function units illustrated with solid linesare operated to execute the data share function according to anembodiment of the present invention. That is, in order to provide thedata share function, the participation receive unit 112, the data obtaintarget notification unit 113, the data transmission unit 115, and thetransmission completion receive unit 116 in the organizer device 100 aare operated; the data transmission unit 115 of the participating device100 b is operated; and the participation notification unit 111 and thedata obtain unit 114 are operated.

<<Organizer Device>>

First, various data used by the organizer device 100 a for controllingcommunication during a data share process is described.

The organizer device 100 a retains (stores) various data such as aparticipant list 20D, an ongoing transmission list 30D, and atransmission completion list 40D (see, for example, FIGS. 4-6).

The participant list 20D includes data for managing the participatingdevice 100 b and the participation requesting device 100 c. Theparticipant list 20D is recorded and stored in a participant liststorage unit 20. The ongoing transmission list 30D includes data formanaging a relationship between the participating device 100 b (i.e. anorigin that transmits shared data (transmitting side), that is, a devicethat has already obtained shared data) and the participation requestingdevice 100 c (i.e. destination that receives the shared data (receivingside)). The ongoing transmission list 30D is recorded and stored in anongoing transmission list storage unit 30. The transmission completionlist 40D includes data for managing a device (formerly participationrequesting device) which has newly become a participating device 100 b(i.e. device which has obtained shared data). The transmissioncompletion list 40D is recorded and stored in a transmission completionlist storage unit 40.

Each of the storage units 20, 30, 40 may be a predetermined storagespace of a storage device (e.g., HDD 108, RAM 104) of the organizerdevice 100 a.

FIG. 4 is a schematic diagram illustrating an example of a dataconfiguration of the participant list 20D according to an embodiment ofthe present invention.

As illustrated in FIG. 4, the participant list 20D includes one or moredata sets in which each set includes data items (e.g., [managementidentifier], [device identifier]) associated to each other. Theorganizer device 100 a uses the participant list 20D to manage theparticipating device 100 b and the participation requesting device 100 cin units of data process apparatuses 100.

The data item [management identifier] of the participant list 20Dindicates identification data used for managing participationnotifications (hereinafter also referred to as “managementidentification data”). An item value included in the data item[management identifier] is, for example, a unique management identifier(unique data number) that is issued when the organizer device 100 areceives a participation notification. The data items [managementidentifier] of FIG. 4 are illustrated as ID numbers issued in an orderin which participation notifications are received by the organizerdevice 100 a. The data item [device identifier] of the participant list20D indicates identification data of participation requesting devices100 c (hereinafter also referred to as “device identification data”). Anitem value included in the data item [device identifier] is, forexample, a unique device identifier (setting value) that is pre-assigned(assigned beforehand) to each data process apparatus 100. The data items[device identifier] of FIG. 4 are illustrated as IP (Internet Protocol)addresses (network setting values) assigned to the data processapparatuses 100.

The data items [management identifier] and [device identifier] of theparticipant list 20D are registered and deleted (managed) in units ofdata sets.

In a case of registering data to the participant list 20D during a phase(stage) where a participation notification is received, the organizerdevice 100 a associates a data item [management identifier] issued tothe participation requesting device 100 c and a data item [deviceidentifier] included in device data obtained from the participationrequesting device 100 c (data obtained upon receiving a participationnotification from the participation requesting device 100 c) andregisters the data item [management identifier] and the data item[device identifier] as a data set based on the order in which theparticipation notification is received. In a case where the organizerdevice 100 a is in a below-described participation notification waitingstate, a data set corresponding to the organizer device 100 a itself isalso registered.

In a case of deleting data from the participant list 20D, a data setincluding a combination of the data item [management identifier] and thedata item [device identifier] is deleted when the event is ended.

Accordingly, the organizer device 100 a manages the participationrequesting devices 100 b and the participating devices 100 b by usingthe participant list 20D.

FIG. 5 is a schematic diagram illustrating an example of a dataconfiguration of the ongoing transmission list 30D according to anembodiment of the present invention.

As illustrated in FIG. 5, the ongoing transmission list 30D includes oneor more data sets in which each set includes two data items of[management identifier] associated to each other. The organizer device100 a uses the ongoing transmission list 30D to manage atransmission/reception relationship between a transmitting device and areceiving device during a data sharing process in units of thetransmission/reception relationships.

The data item [management identifier] of the ongoing transmission list30D indicates management identification data that is issued when theorganizer device 100 a receives a participation notification. Morespecifically, for example, one data item [management identifier]indicates management identification data corresponding to aparticipating device 100 b (which has already obtained shared data)which is a transmission origin of the shared data (hereinafter alsoreferred to as “management identification data of a below-describedtransmission origin device”) and another data item [managementidentifier] indicating management identification data corresponding to aparticipation requesting device 100 c which is a transmissiondestination of the shared data (hereinafter also referred to as“management identification data of a below-described transmissiondestination device”).

The data item [management identifier] of the transmission origin and thedata item [management identifier] of the transmission destination areregistered and deleted (managed) in units of data sets.

In a case of registering data to the ongoing transmission list 30Dduring a phase (stage) where a data sharing process (data transmission)is being performed, the organizer device 100 a associates a data item[management identifier] corresponding to a participating device 100 bwhich is to be the transmission origin (hereinafter also referred to as“transmission origin device”) and a data item [management identifier]corresponding to a participation requesting device 100 c which is to bethe transmission destination (hereinafter also referred to as“transmission destination device”) and registers the item value of thedata item [management identifier] of the transmission origin device andthe item value of the data item [management identifier] of thetransmission destination device as a data set that includes managementidentification data of the transmission origin device and thetransmission destination device.

In a case of deleting data from the ongoing transmission list 30D, adata set including a combination of the data item [managementidentifier] of the transmission origin device and the data item[management identifier] of the transmission destination device isdeleted when the transmission of shared data from the transmissionorigin device to the transmission destination device is completed.

Accordingly, the organizer device 100 a manages the datatransmission/reception relationship between the participating device 100b (transmission origin device) and the participating requesting device100 c (transmission destination device) during a data sharing process byusing the ongoing transmission list 30D.

FIG. 6 is a schematic diagram illustrating an example of a dataconfiguration of the transmission completion list 40D according to anembodiment of the present invention.

As illustrated in FIG. 6, the transmission completion list 40D includesdata items [management identifier]. The organizer device 100 a uses thetransmission completion list 40D to manage participating devices 100 bin units of data process apparatuses 100.

The data item [management identifier] of the transmission completionlist 40D indicates management identification data that is issued whenthe organizer device 100 a receives a participation notification. Morespecifically, for example, data item [management identifier] of thetransmission completion list 40D indicates management identificationdata corresponding to a participation requesting device 100 c (which hascompleted obtaining of shared data) (hereinafter also referred to as“management identification data of a below-described transmissioncompleted device”).

The data items [management identifier] of the transmission completionlist is registered and deleted (managed) in units of data items[management identifier].

In a case of registering data to the transmission completion list 40Dduring a phase (stage) where data transmission is completed, theorganizer device 100 a registers a management identifier correspondingto the participation requesting device (transmission destination device)100 c as an item value of the data item [management identifier]including management identification data of the transmission completeddevice.

In a case of deleting data from the transmission completion list 40D,the data item [management identifier] is deleted when the event isended.

Accordingly, the organizer device 100 a manages participation requestingdevices 100 c which have become participating devices 100 b that haveobtained shared data (transmission completed device).

Returning to the description of the configuration of FIG. 3, theparticipation receive unit 112 is a function unit that receives aparticipation notification from the participation requesting device 100c. The participation receive unit 112 receives the participationnotification, for example, by receiving device data (signal) from theparticipation requesting device 100 c. When the participation receiveunit 112 receives the participation notification, the participationreceive unit 112 accesses the participant list storage unit 20 andregisters the management identification data and the deviceidentification data corresponding to the participation requesting device100 c to the participant list 20D.

The data obtain target notification unit 113 is a function unit thatnotifies a data obtain target from which shared data is to be obtainedby the participation requesting device 100 c. The data obtain targetnotification unit 113 determines a participating device 100 b (dataobtain target) from which shared data is to be obtained by theparticipation requesting device 100 c and notifies the determined dataobtain target (participating device) to the participation requestingdevice 100 c. The determining of the data obtain target is executed by adata obtain target determining unit 1131 included in the data obtaintarget notification unit 113.

The data obtain target determining unit 1131 determines a device (dataobtain target) from one or more participating devices 100 b that hasalready obtained shared data based on, for example, data sharing statusof the participating devices 100 b and the transmission status of theparticipating devices 100 b. An example of the determining process isdescribed as follows.

When the participation receive unit 112 receives a participationnotification, the data obtain target determining unit 1131 accesses theongoing transmission list storage unit 30 and the transmissioncompletion list storage unit 40. The data obtain target determining unit1131 refers to the transmission completion list 40D and obtains themanagement identification data of the transmission completed device thatis registered in the transmission completion list 40D. Further, the dataobtain target determining unit 1131 refers to the ongoing transmissionlist 30D and searches through the data items [management identifier](management identification data of transmission origin device). The dataobtain target determining unit 1131 designates (identifies) themanagement identification data of a transmission completed device whichis not registered as transmission origin device according to the searchresults (i.e. results of searching whether there is managementidentification data of a corresponding device).

For example, the data obtain target determining unit 1131 designates aparticipating device 100 b, which has already obtained shared data andis not transmitting data, from the device(s) found in the search.Thereby, the designated participating device 100 b is determined as thedata obtain target from which shared data is to be obtained by theparticipation requesting device 100 c. In other words, a participatingdevice 100 b, which has already obtained shared data (having shared datastored therein) and is not transmitting shared data to another dataprocess apparatus 100, is designated from the participating devices 100b. In addition, the participating device 100 b may be designated in viewof the work load of transmitting shared data to the participationrequesting device 100 c. Thus, a participating device 100 b, which hasless work load in transmitting shared data to the participationrequesting device 100 c compared to the other participating device(s)100 b, may be designated and determined as the data obtain target.

In a case where the data obtain target determining unit 1131 is unableto designate the participating device 100 b which has already obtainedshared data and is not transmitting data, the data obtain determiningunit 1131 determines the organizer device 100 a as the data obtaintarget. In a case where the data obtain target determining unit 1131designates multiple participating devices 100 b, the participatingdevice 100 b participating earliest in the event (i.e. having theearliest participation order) among the multiple participating devices100 b is determined as the data obtain target. The participation orderto the event may be determined based on, for example, the order of themanagement identification data issued according to the participationorder (order in which the participation notification is received) or theorder in which management identification data is registered (listedorder) in the participant list 20D.

The data obtain target notification unit 113 notifies the participatingdevice 100 b determined by the data obtain target determining unit 1131to the participation requesting device 100 c. More specifically, thedata obtain target notification unit 113 accesses the participant liststorage unit 20 when the participating device 100 b is determined. Then,the data obtain target notification unit 113 refers to the participantlist 20D based on the management identification data corresponding tothe determined participating device 100 b. When the data obtain targetnotification unit 113 finds management identification data that matchesthe management identification data corresponding to the determinedparticipating device 100 b, the data obtain target notification unit 113obtains device identification data associated to the matching managementidentification data (device identification data of a corresponding dataset). Then, the data obtain target notification unit 113 notifies thedata obtain target by transmitting the obtained device identificationdata to the participation requesting device 100 c.

With the data share function according to the above-describedembodiment, the organizer device 100 a, upon receiving a participationrequest from the participation requesting device 100 c, notifies theparticipating device 100 b having already obtained shared data as thedata obtain target to the participation requesting device 100 c, so thatthe shared data can be obtained from the notified participating device100 b.

Further, in a case where the data obtain target notification unit 113notifies the data obtain target to the participation requesting device100 c, the data obtain target notification unit 113 registers a data setto the ongoing transmission list 30D. The data set includes themanagement identification data corresponding to the participating device100 b determined as the data obtain target and the managementidentification data corresponding to the participation requesting device100 c to which the data obtain target is notified. Thereby, theorganizer device 100 a can manage a new data transmission/receptionrelationship between the participating device 100 b (transmission origindevice) and the participating requesting device 100 c (transmissiondestination device) during a data sharing process by using the ongoingtransmission list 30D.

The data transmission unit 115 is a function unit that transmits shareddata in response to a data obtain request from the participationrequesting device 100 c. It is to be noted that the data transmissionunit 115 of the organizer device 100 a transmits shared data in a casewhere the organizer device 100 a is determined as the data obtain targetby the data obtain target determining unit 1131.

In a case where the data obtain request is received, the datatransmission unit 115 responds to the data obtain request bytransmitting shared data stored in a predetermined storage space to theparticipation requesting device 100 c. The predetermined storage spacemay be, for example, a predetermined storage space in a storage deviceof the organizer device 100 a.

After the data transmission unit 115 completes transmitting the shareddata, the data transmission unit 115 notifies that transmission of theshared data is completed to the transmission completion receive unit116.

The transmission completion receive unit 116 is a function unit thatreceives a completion notification notifying the completion of datatransmission during a data sharing process. The transmission completionreceive unit 116 receives the completion notification by receivingdevice identification data of the transmission origin device and deviceidentification data of the transmission destination device from the datatransmission unit 115.

In a case where the data sharing process between the participatingdevice 100 b (determined as the data obtain target) and theparticipation requesting device 100 c is completed, the transmissioncompletion receive unit 116 receives a completion notification of thedata transmission (device identification data of the participatingdevice 100 b and the device identification data of the participationrequesting device 100 c) from the participating device 100 b (datatransmission unit 115 of the participating device 100 b. Further, in acase where the data sharing process between the organizer device 100 a(determined as the data obtain target) and the participation requestingdevice 100 c is completed, the transmission completion receive unit 116receives a completion notification of the data transmission (deviceidentification data of the organizer device 100 a and the deviceidentification data of the participation requesting device 100 c) fromthe data transmission unit 115 of the organizer device 100 a.

When the transmission completion receive unit 116 receives thecompletion notification of the data transmission, the transmissioncompletion receive unit 116 accesses the transmission completion liststorage unit 40 and registers the management identification datacorresponding to the participation requesting device 100 c which hasobtained shared data (i.e. transmission completed device) to thetransmission completion list 40D. More specifically, in registering themanagement identification corresponding to the participation requestingdevice 100 c, the transmission completion receive unit 116 accesses theparticipant list storage unit 20. Then, the transmission completionreceive unit 116 refers to the participant list 20D based on the deviceidentification data of the participation requesting device 100 cincluded in the completion notification. When the transmissioncompletion receive unit 116 finds device identification data thatmatches the device identification data of the participation requestingdevice 100 c, the transmission completion notification unit 116 obtainsmanagement identification data associated to the matching deviceidentification data (management identification data of a correspondingdata set). Thereby, the organizer device 100 a can manage thetransmission completed devices with the transmission completion list40D.

Further, when the transmission completion receive unit 116 receives thecompletion notification of the data transmission, the transmissioncompletion receive unit 116 accesses the ongoing transmission liststorage unit 30 and deletes the data set including the managementidentification data of the transmission origin device and thetransmission destination device (which have completed the data sharingprocess) from the ongoing transmission list 30D. More specifically, indeleting the data set, the transmission completion receive unit 116accesses the ongoing transmission list storage unit 30. Then, thetransmission completion receive unit 116 refers to the ongoingtransmission list 30D based on the management identification data of thetransmission origin device (participating device 100 b) and themanagement identification data of the transmission destination device(participation requesting device 100 c) obtained when registering themanagement identification data to the transmission completion list 40D.When the transmission completion receive unit 116 finds managementidentification data that matches the management identification data ofthe transmission destination device and the management identificationdata of the transmission origin device associated to the managementidentification data of the transmission destination device(corresponding data set), the transmission completion notification unit116 deletes the management identification data of both the transmissionorigin device and the transmission destination device (correspondingdata set) from the ongoing transmission list 30D. Thereby, the organizerdevice 100 a can manage the transmission completed devices with thetransmission completion list 40D. It is to be noted that the managementidentification data of the transmission origin device may be obtainedwith the same method as obtaining the management identification data ofthe transmission destination data.

<<Participating Device>>

In a case where the data transmission unit 115 of the participatingdevice 100 b receives a data obtain request from the participationrequesting device 100 c, the data transmission unit 115 responds bytransmitting shared data stored in a predetermined storage space of astorage device of the participating device 100 b to the participationrequesting device 100 c.

After the data transmission unit 115 completes transmitting the shareddata to the participation requesting device 100 c, the data transmissionunit 115 notifies completion of the transmission of the shared data(completion notification) to, for example, the organizer device 100 a(transmission completion receive unit 116).

It is to be noted that the destination of the completion notificationtransmitted by the data transmission unit 115 differs according to thedata process apparatus 100 (operation environment) in which the datatransmission unit 115 operates. That is, the destination of thecompletion notification differs depending on whether the data processapparatus 100 is the organizer device 100 a or the participating device100 b. Accordingly, the data transmission unit 115 switches thedestination of the completion notification in accordance with theoperation environment of the data transmission unit 115. For example,first, the data transmission unit 115 determines whether the operationenvironment of the data transmission unit 115 itself is the organizerdevice 100 a or the participating device 100 b. In a case where theoperation environment of the data transmission unit 115 is theparticipating device 100 b, the data transmission unit 115 sets thedestination of the completion notification to the organizer device 100a. On the other hand, in a case where the operation environment of thedata transmission unit 115 is the organizer device 100 a, the datatransmission unit 115 sets the destination of the completionnotification to the transmission completion receive unit 116 of theorganizer device 116. The operation environment may be determined basedon, for example, whether each of the participant list 20, the ongoingtransmission list 30, and the transmission completion storage list 40 isstored in the data process apparatus 100.

<<Participation Requesting Device>>

The participation notification unit 111 is a function unit that notifiesparticipation to an event. When the participation requesting device 100c detects a network of an event and succeeds in connecting to thenetwork, the participation notification unit 111 of the participationrequesting device 100 c notifies participation to the organizer device100 a (participation receive unit 112).

The data obtain unit 114 is a function unit that request obtaining ofshared data. The data obtain unit 114 of the participation requestingunit 11 c request obtaining of shared data to the organizer device 100 aor the participating device 100 b notified as the data obtain target bythe organizer device 100 a (data obtain target notification unit 113).Then, the data obtain unit 114 accesses the organizer device 100 a orthe participating device 100 b based on, for example, deviceidentification data received from the data obtain target notificationunit 113 and requests obtaining of shared data.

Hence, with the data share function according to the above-describedembodiment, the workload for obtaining shared data is distributed amongthe data process apparatuses 100.

The data share function according to the above-described embodiment isperformed by cooperatively operating the above-described function units.It is to be noted that each of the function units are operated by a datashare program (software having a data share function) installed in oneor more data process apparatuses 100 constituting the data share system1000 in which the data share program is loaded from a storage device(e.g., HDD 108, ROM 105) of the data process apparatus 100 or acomputer-readable recording medium (e.g., 103 a) to a memory (e.g., RAM104) of the data process apparatus 100 and executed by a processor(e.g., CPU 106) of the data process apparatus 100.

<<Data Sharing Process>>

The data sharing process according to an embodiment of the presentinvention is performed in two instances of the data share system 1000.

In one instance, the data sharing process is performed when theorganizer device 100 a, being a participation notification waitingstate, receives a participation notification from a participationrequesting device 100 c in a case where there is no participating device100 b in the data share system 1000 (receiving a participationnotification for the first time).

In another instance, the data sharing process is performed when theorganizer device 100 a, being in a participation notification waitingstate, receives a participation notification from a participationrequesting device 100 c in a case where there is a participating device100 b in the data share system 1000 (receiving another participationnotification after receiving the participation request for the firsttime).

Next, the data sharing process is described with respect to eachinstance. In the following, the organizer device 100 a (i.e. dataprocess apparatus 100 of the organizer of an event) is indicated asdevice [1] 100 ₁, the participating device 100 b or the participationrequesting device 100 c is indicated as device [2] 100 ₂ or device [3]100 ₃ for the sake of convenience.

[Instance 1]: Case where an Organizer Device Receives a ParticipationNotification for the First Time

FIG. 7 is a sequence diagram illustrating steps in a case of performinga data sharing process (part 1) according to an embodiment of thepresent invention. FIGS. 8A-8D are schematic diagrams illustratingtransition of data of the participant list 20D, the ongoing transmissionlist 30D, the transmission completion list 40D in a case of performingthe data sharing process (part 1) according to an embodiment of thepresent invention.

As illustrated in FIG. 7, the participation receive part 112 of thedevice [1] 100 ₁ receives a participation notification indicatingparticipation to an event from the participation notification unit 111of the device [2] 100 ₂ (Step S101). In this step, the participationnotification unit 111 transmits device data of the device [2] 100 ₂together with the participation request to the participation receivepart 112 of the device [1] 100 ₁.

When the device [1] 100 ₁ receives the participation notification, thefunction units of the device [1] 100 ₁ performs the following steps.

First, the participation receive unit 112 registers the device [2] 100 ₂to the participant list 20D (Step S102). In this step, the participationreceive unit 112 accesses the participant list storage unit 20 andrefers to the participant list 20D. The participation receive unit 112registers a new data set that includes management identification data(ID value) issued to the device [2] 100 ₂ upon reception of theparticipation notification and device identification data (IP address)obtained from the device [2] 100 ₂. As a result, there is a transitionof data in the participant list 20D as illustrated in FIG. 8A. Morespecifically, the transition of data is described as follows.

First, an ID value 1′ of the device [1] 100 ₁ and an IP address'192.168.11.010′ of the device [1] 100 ₁ are already registered in theparticipant list 20D. In this state, when Step S102 is executed, an IDvalue 2′ of the device [2] 100 ₂ and an IP address' 192.168.11.011′ ofthe device [2] 100 ₂ are registered as data indicating a newparticipation requesting device 100 c.

Then, returning to FIG. 7, the participation receive unit 112 instructsthe data obtain target notification unit 113 to notification a dataobtain target to the device [2] 100 ₂ (Step S103).

In response to the instruction from the participation receive unit 112,the data obtain target notification unit 113 refers to the lists 20D,30D, and 40D and determines the data obtain target based on, forexample, a data sharing status and/or a data transmitting status of aparticipating device 100 b (Step S104). As a result, the data obtaintarget notification unit 113 determines the device [1] 100 ₁ as the dataobtain target because there is not one participating device. The processof determining the data obtain target is described below in furtherdetail with reference to FIG. 13.

The data obtain target notification unit 113 notifies the determineddata obtain target to the device [2] 100 ₂ (Step S105). In this step,the data obtain target notification unit 113 transmits the dataidentification data (IP address) of the device [1] 100 ₁ which has beendetermined as the data obtain target.

Then, the data obtain target notification unit 113 registers the device[1] 100 ₁ (i.e. device determined as data obtain target) in associationwith the device [2] 100 ₂ (i.e. device of transmission destination(participation requesting device 100 c)) to the ongoing transmissionlist 30D (Step S106). In this step, the data obtain target notificationunit 113 accesses the ongoing transmission list storage unit 30 andrefers to the ongoing transmission list 30D. Then, the data obtaintarget notification unit 113 registers a new data set including themanagement identification data (ID value) of the device [1] 100 ₁ andthe management identification data (ID value) of the device [2] 100 ₂ tothe ongoing transmission list 30D. As a result, there is a transition ofdata in the ongoing transmission list 30D as illustrated in FIG. 8B.More specifically, the transition of data is described as follows.

First, the values of the data items of the ongoing transmission list 30Dare null because there is no ongoing communication(transmission/reception) of shared data being currently performed.Therefore, in this state, when Step S106 is executed, an ID value 1′ ofthe device [1] 100 ₁ (transmission origin) and an ID value 2′ of thedevice [2] 100 ₂ (transmission destination) are registered as dataindicating a new transmission/reception relationship between a device ofthe transmission origin (transmitting device) and a device of thetransmission destination (receiving device).

Then, returning to FIG. 7, the data obtain unit 114 of the device [2]100 ₂ requests the device [1] 100 ₁ (data transmission unit 115) toobtain shared data (Step S107). In this step, the data obtain unit 114accesses the device [1] 100 ₁ based on the device identification data(IP address) obtained upon receiving the notification of the data obtaintarget and obtains shared data from the data transmission unit 115.

In response to the request from the data obtain unit 114, the datatransmission unit 115 of the device [1] 100 ₁ transmits the shared datato the device [2] 100 ₂ (data obtain unit 114) (Step S108).

Then, the data transmission unit 115 notifies completion of thetransmission of the shared data to the transmission completion receiveunit 116 (Step S109). In this step, the data transmission unit 115provides the device identification data (IP address) of the device [1]100 ₁ (transmitting device) and the device identification data (IPaddress) of the device [2] 100 ₂ (receiving device).

In response to the notification from the data transmission unit 115, thetransmission completion receive unit 116 registers the device [2] 100 ₂that has obtained the shared data (transmission completed device) to thetransmission completion list 40D (Step S110). In this step, thetransmission completion receive unit 116 accesses the participant liststorage unit 20, refers to the participant list 20D based on the deviceidentification data (IP address) obtained from the data transmissionunit 115, and obtains the management identification data (ID value) ofthe device [1] 100 ₁ (transmitting device) and the managementidentification data (IP value) of the device [2] 100 ₂ (receivingdevice). Further, the transmission completion receive unit 116 accessesthe transmission completion list storage unit 40 and refers to thetransmission completion list 40D. The transmission completion receiveunit 116 registers new data indicating the management identificationdata (ID value) of the device [2] 100 ₂ obtained from the datatransmission unit 15 to the transmission completion list 40D. As aresult, there is a transition of data in the transmission completionlist 40D as illustrated in FIG. 8C. More specifically, the transition ofdata is described as follows.

First, an ID value 1′ of the device [1] 100 ₁ is already registered inthe transmission completion list 40D. In this state, when Step S110 isexecuted, an ID value 2′ of the device [2] 100 ₂ is registered as dataindicating a new transmission completed device.

Then, returning to FIG. 7, the transmission completion receive unit 116updates the ongoing transmission list 30D in accordance with the statusof the data sharing (transmission) between the device [1] 100 ₁ and thedevice [2] 100 ₂ (Step S111). In this step, the transmission completionreceive unit 116 accesses the ongoing transmission list storage unit 30,refers to the ongoing transmission list 30D based on the managementidentification data (ID value) of the device [1] 100 ₁ (transmittingdevice) and the management identification data (ID value) obtained fromthe data transmission unit 115, and identifies a data set includingcorresponding (matching) management identification data. Then, thetransmission completion receive unit 116 deletes the identified data setand updates the ongoing transmission list 30D. As a result, there is atransition of data in the ongoing transmission completion list 30D asillustrated in FIG. 8D. More specifically, the transition of data isdescribed as follows.

First, the ID value 1′ of the device [1] 100 ₁ (transmitting device) andthe ID value 2′ of the device [2] 100 ₂ (receiving device) which haveperformed transmission/reception of shared data are registered in theongoing transmission list 30D. In this state, when Step S111 isexecuted, a corresponding data set that includes the ID value 1′ of thedevice [1] 100 ₁ (transmitting device) and the ID value 2′ of the device[2] 100 ₂ (receiving device) is deleted from the ongoing transmissionlist 30D, so that the values of the data items in the ongoingtransmission list 30D becomes null. Thereby, the data indicating thetransmission/reception relationship between the transmitting device andthe receiving device is updated.

Hence, with the data share system 1000 according to the above-describedembodiment, a data sharing process including operations (actions)illustrated in FIG. 9 can be performed by the data sharing process ofFIG. 7.

FIG. 9 is a schematic diagram illustrating actions performed in a datasharing operation (part 1) according to an embodiment of the presentinvention. First, when the device [1] 100 ₁ waiting for a participationnotification receives a participation notification from the device [2]100 ₂ (operation 1), the device [1] 100 ₁ notifies to the device [2] 100₂ that the device [1] 100 ₁ (organizer device) is the data obtain targetfrom which shared data is to be obtained (operation 2). Then, the device[2] 100 ₂ becomes a state where data sharing (obtaining shared data)with respect to the device [1] 100 ₁ is ongoing (operation 3).

[Instance 2]: Case where an Organizer Device Receives a NextParticipation Notification

FIG. 10 is a sequence diagram illustrating steps performed in a case ofperforming a data sharing process (part 2) according to an embodiment ofthe present invention. FIGS. 11A-11D are schematic diagrams illustratingtransition of data of the participant list 20D, the ongoing transmissionlist 30D, the transmission completion list 40D in a case of performingthe data sharing process (part 2) according to an embodiment of thepresent invention.

The data sharing process illustrated in FIG. 10 illustrates steps thatare performed after the data sharing process of FIG. 7. In other words,FIG. 10 illustrates processes performed in a case where the device [3]100 ₃ (a new participation requesting device 100 c) is connected to thedata share system 1000 having the device [2] 100 ₂ (participating device100 b that has already obtained shared data) connected to the device [1]100 ₁ (organizer device 100 a). In the following description of the datasharing process of FIG. 10, the steps similar to those of the FIG. 7 arenot described in further detail.

When the device [1] 100 ₁ receives a participation notification, thefunction units of the device [1] 100 ₁ performs the following steps.

First, the participation receive unit 112 registers the device [3] 100 ₃to the participant list 20D (Step S202). In this step, the participationreceive unit 112 registers a new data set that includes managementidentification data (ID value) issued to the device [3] 100 ₃ uponreception of the participation notification and device identificationdata (IP address) obtained from the device [3] 100 ₃. As a result, thereis a transition of data in the participant list 20D as illustrated inFIG. 11A. More specifically, the transition of data is described asfollows.

First, the ID value 1′ of the device [1] 100 ₁ and the IP address'192.168.11.010′ of the device [1] 100 ₁ and the ID value 2′ of thedevice [2] 100 ₂ and the IP address' 192.168.11.011′ of the device [2]100 ₂ are already registered in the participant list 20D. In this state,when Step S202 is executed, an ID value 3′ of the device [3] 100 ₃ andan IP address' 192.168.11.012′ of the device [3] 100 ₃ are registered asdata indicating a new participation requesting device 100 c.

Then, returning to FIG. 10, the participation receive unit 112 instructsthe data obtain target notification unit 113 to notify a data obtaintarget to the device [3] 100 ₃ (Step S203).

In response to the instruction from the participation receive unit 112,the data obtain target notification unit 113 refers to the lists 20D,30D, and 40D and determines the data obtain target based on, forexample, a data sharing status and/or a data transmitting status of aparticipating device 100 b (Step S204). As a result, because the device[2] 100 ₂ is a participating device that has already obtained shareddata (i.e. participating device 100 b), the data obtain targetnotification unit 113 determines the device [2] 100 ₂ as the data obtaintarget. The process of determining the data obtain target is describedbelow in further detail with reference to FIG. 13.

The data obtain target notification unit 113 notifies the determineddata obtain target to the device [3] 100 ₃ (Step S205). In this step,the data obtain target notification unit 113 transmits the dataidentification data (IP address) of the device [2] 100 ₂ which has beendetermined as the data obtain target.

Then, the data obtain target notification unit 113 registers the device[2] 100 ₂ (i.e. device determined as data obtain target) in associationwith the device [3] 100 ₃ (i.e. device of transmission destination(participation requesting device 100 c)) to the ongoing transmissionlist 30D (Step S206). In this step, the data obtain target notificationunit 113 registers a new data set including the managementidentification data (ID value) of the device [2] 100 ₂ and themanagement identification data (ID value) of the device [3] 100 ₃ to theongoing transmission list 30D. As a result, there is a transition ofdata in the ongoing transmission list 30D as illustrated in FIG. 11B.More specifically, the transition of data is described as follows.

First, the values of the data items of the ongoing transmission list 30Dare null because there is no ongoing communication(transmission/reception) of shared data being currently performed.Therefore, in this state, when Step S206 is executed, an ID value 2′ ofthe device [2] 100 ₂ (transmission origin) and an ID value 3′ of thedevice [3] 100 ₃ (transmission destination) are registered as dataindicating a new transmission/reception relationship between a device ofthe transmission origin (transmitting device) and a device of thetransmission destination (receiving device).

Then, returning to FIG. 10, the data obtain unit 114 of the device [3]100 ₃ requests the device [2] 100 ₂ (data transmission unit 115) toobtain shared data (Step S207). In this step, the data obtain unit 114accesses the device [2] 100 ₂ based on the device identification data(IP address) obtained upon receiving the notification of the data obtaintarget and obtains shared data from the data transmission unit 115.

In response to the request from the data obtain unit 114, the datatransmission unit 115 of the device [2] 100 ₂ transmits the shared datato the device [3] 100 ₃ (data obtain unit 114) (Step S208).

Then, the data transmission unit 115 notifies completion of thetransmission of the shared data to the device [1] 100 ₁ (transmissioncompletion receive unit 116) (Step S209). In this step, the datatransmission unit 115 provides the device identification data (IPaddress) of the device [2] 100 ₂ (transmitting device) and the deviceidentification data (IP address) of the device [3] 100 ₃ (receivingdevice).

In response to the notification from the data transmission unit 115, thetransmission completion receive unit 116 registers the device [3] 100 ₃that has obtained the shared data (transmission completed device) to thetransmission completion list 40D (Step S210). In this step, thetransmission completion receive unit 116 refers to the participant list20D based on the device identification data (IP address) obtained fromthe data transmission unit 115 and obtains the management identificationdata (ID value) of the device [2] 100 ₂ (transmitting device) and themanagement identification data (IP value) of the device [3] 100 ₃(receiving device). Further, the transmission completion receive unit116 registers new data indicating the management identification data (IDvalue) of the device [3] 100 ₃ obtained from the data transmission unit15 to the transmission completion list 40D. As a result, there is atransition of data in the transmission completion list 40D asillustrated in FIG. 11C. More specifically, the transition of data isdescribed as follows.

First, the ID value 1′ of the device [1] 100 ₁ and the ID value 2′ ofthe device [2] 100 ₂ are already registered in the transmissioncompletion list 40D. In this state, when Step S210 is executed, an IDvalue 3′ of the device [3] 100 ₃ is registered as data indicating a newtransmission completed device.

Then, returning to FIG. 10, the transmission completion receive unit 116updates the ongoing transmission list 30D in accordance with the statusof the data sharing (transmission) between the device [2] 100 ₂ and thedevice [3] 100 ₃ (Step S211). In this step, the transmission completionreceive unit 116 refers to the ongoing transmission list 30D based onthe management identification data (ID value) of the device [2] 100 ₂(transmitting device) and the management identification data (ID value)obtained from the data transmission unit 115 and identifies a data setincluding corresponding (matching) management identification data. Then,the transmission completion receive unit 116 deletes the identified dataset and updates the ongoing transmission list 30D. As a result, there isa transition of data in the ongoing transmission completion list 30D asillustrated in FIG. 11D. More specifically, the transition of data isdescribed as follows.

First, the ID value 2′ of the device [2] 100 ₂ (transmitting device) andthe ID value 2′ of the device [2] 100 ₂ (receiving device) which haveperformed transmission/reception of shared data are registered in theongoing transmission list 30D. In this state, when Step S211 isexecuted, a corresponding data set that includes the ID value 2′ of thedevice [2] 100 ₂ (transmitting device) and the ID value 3′ of the device[3] 100 ₃ (receiving device) is deleted from the ongoing transmissionlist 30D, so that the values of the data items in the ongoingtransmission list 30D becomes null. Thereby, the data indicating thetransmission/reception relationship between the transmitting device andthe receiving device is updated.

Hence, with the data share system 1000 according to the above-describedembodiment, a data sharing process including operations (actions)illustrated in FIG. 12 can be performed by performing the data sharingprocess of FIG. 10 after performing the data sharing process of FIG. 7.

FIG. 12 is a schematic diagram illustrating actions performed in a datasharing operation (part 2) according to an embodiment of the presentinvention. First, when the device [1] 100 ₁ waiting for a participationnotification receives a participation notification from the device [3]100 ₃ (operation 4), the device [1] 100 ₁ notifies to the device [3] 100₃ that the device [2] 100 ₂ (which has already obtained shared data) isthe data obtain target from which the shared data is to be obtained(operation 5). Then, the device [3] 100 ₃ becomes a state where datasharing (obtaining shared data) with respect to the device [2] 100 ₂ isongoing (operation 6). Then, after the transmission of the shared datato the device [3] 100 ₃ is completed, the device [2] 100 ₂ notifies tothe device [1] 100 ₁ that the transmission of the shared data iscompleted (operation 7).

Hence, with the data share function according to the above-describedembodiment, data sharing processes with respect to multiple data processapparatuses are not performed entirely by the organizer device 100 a.Instead, the workload of the processes can be distributed among one ormore other data process apparatuses 100 including not only the organizerdevice 100 a but also one or more participating devices 100 b which havealready obtained the shared data.

<<Process of Determining Data Obtain Target>>

FIG. 13 is a flowchart illustrating an example of a process ofdetermining a data obtain target according to an embodiment of thepresent invention. In FIG. 13, the process of determining a data obtaintarget of Step S104 of FIG. 7 and Step S204 of FIG. 10 is illustrated indetail. In other words, processes performed by the data obtain targetdetermining unit 1131 included in the data obtain target notificationunit 113 of the organizer device 100 a are illustrated in FIG. 13.

With reference to FIG. 13, the data obtain target determining unit 1131identifies a participating device 100 b which has already obtainedshared data and is not currently transmitting any data (Step S302). Inthis step, the data obtain target determining unit 1131 accesses theongoing transmission list storage unit 30 and the transmissioncompletion list storage unit 40. The data obtain target determining unit1131 refers to the transmission completion list 40D and obtains themanagement identification data (ID value) of one or more registereddevices which has completed transmission of shared data. The data obtaintarget determining unit 1131 refers to the ongoing transmission list 30Dand identifies the management identification data of a transmissioncompleted device which does not match the management identification dataof the transmitting device (transmission origin) registered in theongoing transmission list 30D. As a result, the data obtain targetdetermining unit 1131 identifies one or more participating devices 100 bthat correspond to the identified management identification data. Theone or more participating devices 100 b identified by the data obtaintarget determining unit 1131 are participating devices 100 b which haveobtained shared data and are not currently transmitting shared data.

Then, the data obtain target determining unit 1131 determines whetherany participating devices 100 b have been identified (whether there areany identified data) (Step S302).

In a case where no participating device 100 b is identified (noidentified data) (No in Step S302), the data obtain target determiningunit 1131 determines that the organizer device 100 a is the data obtaintarget (Step S303). Accordingly, the data obtain target determining unit1131 transmits the device identification data (IP address) of theorganizer device 100 a to the participation requesting device 100 c.

On the other hand, in a case where one or more participating devices isidentified (existence of identified data) (Yes in Step S302), the dataobtain target determining unit 1131 determines whether multiplesparticipating devices 100 b are identified (multiple corresponding data)(Step S304).

In a case where the data obtain target determining unit 1131 determinesthat one participating device 100 b is identified (No in Step S304), thedata obtain target determining unit 1131 determines the identifiedparticipating device 100 b as the data obtain target (Step S305).Thereby, the data obtain target notification unit 113 transmits thedevice identification data (IP address) of the determined participatingdevice 100 b to the participation requesting device 100 c. In order totransmit the device identification data, the data obtain targetnotification unit 113 accesses the participant list storage unit 20.Then, the data obtain target notification unit 113 refers to theparticipant list 20D and obtains the device identification data (IPaddress) associated to the management identification data (correspondingdata) obtained from the results of performing the above-describedprocess of searching management identification data. Thereby, the dataobtain target notification unit 113 obtains the device identificationdata of the participating device 100 b determined as the data obtaintarget.

On the other hand, in a case where multiple participating devices 100 bare identified (plural corresponding data identified) (Yes in StepS304), the data obtain target notification unit 113 determines oneparticipating device 100 b as the data obtain target from the multipleidentified participating devices 100 b (Step S306). The oneparticipating device 100 b determined as the data obtain target is adevice participating earliest in the event among the multipleparticipating devices 100 b. In this step, the data obtain targetdetermining unit 1131 determines the order of participation in the eventbased on the management identification data (corresponding data)obtained from the results of performing the above-described process ofsearching management identification data. For example, in a case wherethe management identification data (ID value) is issued in accordancewith the order of participation in the event (order in which theparticipation notification is received), the data obtain targetdetermining unit 1131 compares the ID values obtained from the resultsof performing the above-described process of searching managementidentification data and determines the participating device 100 b to bethe data obtain target from the multiple participating devices 100 bbased on the comparison results. For example, the participating device100 b having the lowest ID value is determined as the data obtaintarget. The participating device 100 b having the lowest ID value maybe, for example, a participating device 100 b having the least amount ofworkload for transmitting data to the participation requesting device100 a.

Hence, with the process of determining the data obtain target accordingto the above-described embodiment, the participating device 100 b whichhas obtained shared data (storing shared data therein), is not currentlytransmitting shared data to other data process apparatuses 100, andhaving the least amount of workload for transmitting data to theparticipation requesting device 100 c.

<<Example of Operations of a Data Sharing Process>>

With the data share system 1000 according to the above-describedembodiment, a data sharing operation performed in various instances ofreceiving a participation notification from a new participationrequesting device is described below.

FIGS. 14A and 14B are schematic diagrams illustrating operationsperformed in a data sharing operation (part 3) according to anembodiment of the present invention. FIGS. 14A and 14B illustrate a caseof connecting a new device [4] 100 ₄ as a new participation requestingdevice 100 c to the data share system 1000 having the device [1] 100 ₁(organizer device 100 a) and the device [2] 100 ₂ (participating device100 b) connected each other in a state where data sharing is ongoingbetween the device [2] 100 ₂ and the device [3] 100 ₃ (shared data beingcurrently transmitted from the device [2] 100 ₂ to the device [3] 100₃).

As illustrated in FIG. 14A, the device [1] 100 ₁ waiting for aparticipation notification receives a participation notification fromthe device [3] 100 ₃ (operation 1). Because the device [2] 100 ₂ hasalready obtained shared data, the device [1] 100 ₁ determines the device[2] 100 ₂ as the data obtain target. Then, the device [1] 100 ₁ notifiesto the device [3] 100 ₃ that the device [2] 100 ₂ is the data obtaintarget from which shared data is to be obtained (operation 2). Thereby,the device [2] 100 ₂ becomes a state where data sharing (obtainingshared data) with respect to the device [1] 100 ₁ is ongoing (operation3). In this state, the device [1] 100 ₁ waiting for a participationnotification receives a participation notification from the device [4]100 ₄ (operation 4).

As illustrated in FIG. 14B, when the device [1] 100 ₁ receives theparticipation notification from the device [4] 100 ₄, the device [1] 100₁ determines the device [1] 100 ₁ itself as the data obtain targetbecause transmission of shared data from the device [2] 100 ₂ to thedevice [3] 100 ₃ is ongoing (operation 5). Thereby, the device [4] 100 ₄becomes a state where data sharing (obtaining shared data) with respectto the device [1] 100 ₁ is ongoing (operation 5). In this state, thedevice [1] 100 ₁ waiting for a participation notification receives aparticipation notification from the device [4] 100 ₄ (operation 4).Then, after the device [2] 100 ₂ completes transmitting shared data tothe device [3] 100 ₃, the device [2] 100 ₂ notifies to the device [1]100 ₁ that the transmission of shared data is completed (operation 7).In this state, the device [3] 100 ₃ has obtained shared data.

FIGS. 15A and 15B are schematic diagrams illustrating operations(actions) performed in a data sharing process (part 4) according to anembodiment of the present invention. FIGS. 16A and 16B are schematicdiagrams illustrating operations performed in a data sharing operation(part 5) according to an embodiment of the present invention.

FIGS. 15A-16B illustrate a case of connecting new devices [5] 100 ₅, [6]100 ₆ as new participation requesting devices 100 c to the data sharesystem 1000 having the device [2] 100 ₂ and the device [3] 100 ₃(participating devices 100 b) connected to the device [1] 100 ₁(organizer device 100 a) in a state where data sharing is ongoingbetween the device [1] 100 ₁ and the device [2] 100 ₂ (shared data beingcurrently transmitted from the device [1] 100 ₁ to the device [2] 100₂).

As illustrated in FIG. 15A, the device [2] 100 ₂ notifies to the device[1] 100 ₁ that the transmission of shared data is completed (operation7). Then, the device [1] 100 ₁ waiting for a participation notificationreceives a participation notification from the device [5] 100 ₅(operation 8).

As illustrated in FIG. 15B, in a case where the device [1] 100 ₁receives a participation notification from the device [6] 100 ₆, thedevice [1] 100 ₁ determines the device [2] 100 ₂ as the data obtaintarget because the device [2] 100 ₂ is the one having an earlierparticipation order among the devices [2] 100 ₂ and [3] 100 ₃ (both ofwhich having obtained shared data and not currently transmitting shareddata). Accordingly, the device [1] 100 ₁ notifies to the device [5] 100₅ that the device [2] 100 ₂ is the data obtain target (operation 9).Thereby, the device [5] 100 ₅ becomes a state where data sharing(obtaining shared data) with respect to the device [2] 100 ₂ is ongoing(operation 10). It is to be noted that, after the device [4] 100 ₄completes data sharing with the device [1] 100 ₁, the device [4] 100 ₄becomes a state where shared data is obtained. In this state, the device[1] 100 ₁ waiting for a participation notification receives aparticipation notification from the device [6] 100 ₆ (operation 11).

As illustrated in FIGS. 15B and 16A, in a case where the device [1] 100₁ receives a participation notification from the device [6] 100 ₆, thedevice [1] 100 ₁ determines the device [3] 100 ₃ as the data obtaintarget because the device [3] 100 ₃ is the one having an earlierparticipation order among the devices [3] 100 ₃ and [4] 100 ₄ (both ofwhich having obtained shared data and not currently transmitting shareddata). Accordingly, the device [1] 100 ₁ notifies to the device [6] 100₆ that the device [3] 100 ₃ is the data obtain target (operation 12).Thereby, the device [6] 100 ₆ becomes a state where data sharing(obtaining shared data) with respect to the device [3] 100 ₃ is ongoing(operation 13).

As illustrated in FIG. 16B, after the device [2] 100 ₂ completestransmitting shared data to the device [5] 100 ₅, the device [2] 100 ₂notifies to the device [1] 100 ₁ that transmission of shared data iscompleted (operation 14). Thereby, the device [5] 100 ₅ becomes a statewhere shared data is obtained. Further, after the device [3] 100 ₃completes transmitting shared data to the device [6] 100 ₆, the device[3] 100 ₃ notifies to the device [1] 100 ₁ that transmission of shareddata is completed (operation 15). Thereby, the device [6] 100 ₆ becomesa state where shared data is obtained.

With the data process apparatus 100 according to the above-describedembodiment, in a case where the data process apparatus 100 is theorganizer device 100 a, the participation receive unit 112 of theorganizer device 100 a receives a notification requesting participationto an event (participation notification) from the participationrequesting device 100 b. Then, the data obtain target notification unit113 of the device [1] 100 ₁ notifies to the participation requestingdevice 100 c that the participating device 100 b (from which aparticipation notification is already received) is the data obtaintarget. In notifying the data obtain target, the obtain targetdetermining unit 1131 of the data obtain target notification unit 113determines the data obtain target (device from which the participationrequesting device 100 c is to obtain shared data) from one or moreparticipating devices 100 b based on, for example, the data share statusand the data transmission status of the one or more participatingdevices 100 b. As a result, the participation requesting device 100 cobtains shared data from the device notified by the device [1] 100 ₁.

Accordingly, with the data share system 1000 according to theabove-described embodiment, the workload for obtaining shared data canbe distributed among multiple data process apparatuses 100. As a result,data sharing can be efficiently performed with reduced workload.

Modified Example 1

Next, a modified example 1 (first modified example) of the presentinvention is described.

FIGS. 17A and 17B are schematic diagrams illustrating a data sharesystem 1010 according to the first modified example. The differencebetween the configuration of the data share system 1010 of FIG. 17A andthe configuration of the data share system 1000 of FIG. 1A is that aprojection apparatus (projector) 200 is connected to the datatransmission path N.

The projection apparatus 200 is a device including a wirelesscommunication function and a data display function (e.g., projector).

FIG. 17B illustrates a case where the data share system 1010 of thefirst modified example is used for a conference presentation. In thiscase, display contents, which are based on shared data, are not onlydisplayed on the data process apparatuses 100 ₂, 100 ₃ of the viewersbut are also projected to a screen by the projection apparatus 200.

Similar to the above-described data process apparatus 100, theprojection apparatus 200 includes hardware that enable a screen to beshared among multiple data process apparatuses 100.

FIG. 18 is a schematic diagram illustrating an example of a hardwareconfiguration of the projection apparatus 200 according to the firstmodified example. As illustrated in FIG. 18, the projection apparatus200 includes, for example, a controller 210, a control panel 220, and aprojection device 230 that are connected to each other by a bus B.

The control panel 220 includes, for example, an input unit and a displayunit. The control panel 220 is for providing various data (e.g., devicedata) to the user and receiving various maneuvers by the user in orderto, for example, input settings or input instructions to the projectionapparatus 200. The projection device 230 is for projecting image dataonto a screen.

The controller 210 includes a control board having, for example, a CPU211, a storage device 212, a network I/F 213, and an external storageI/F 214 that are connected to each other by the bus B.

The storage device 211 includes, for example, a RAM, a ROM, a HDD whichretain and store various programs and data therein. The CPU 106includes, for example, a processor that controls the entire data processapparatus 100 and executes functions of the data process apparatus 100by obtaining data and programs from, for example, the HDD 108 or the ROM105 and loading the data and programs to the RAM (memory) 104, andexecuting various processes. The CPU 212 includes a processor thatcontrols the entire projection apparatus 200 and executes functions ofthe projection apparatus 200 by obtaining data and programs from, forexample, the HDD or the ROM and loading the data and programs to the RAM(memory), and executing various processes.

The network I/F 213 is an interface that connects the projectionapparatus 200 to the data transmission path N. Thereby, the projectionapparatus 200 can perform data communications with the one or more dataprocess apparatuses 100 by way of the network I/F 213.

The external I/F 214 is an interface that connects the projectionapparatus 200 to an external storage device such as a computer-readablerecording medium 214 a. The computer-readable recording medium 214 aincludes, for example, an SD (Secure Digital) memory card or a USB(Universal Serial Bus) memory. Accordingly, the projection apparatus 200reads data from the computer-readable recording medium 214 a and/orwrites data to the computer-readable recording medium 214 a by way ofthe external I/F 214.

Accordingly, with the projection apparatus 200 according to the firstmodified example having the above-described hardware configuration, adata share program (software having a data share function), which isinstalled in the projection apparatus 200 constituting the data sharesystem 1010, is executed by loading the data share program from thestorage device 212 to the memory (e.g., RAM) of the projection apparatus100 and executed by the processor (e.g., CPU 211) of the projectionapparatus 200.

Hence, substantially the same effects (advantages) as those of the datashare system 1010 can be attained with the data share system 1010according to the first modified example.

Modified Example 2

Next, a modified example 2 (second modified example) of the presentinvention is described.

FIGS. 19A and 19B are schematic diagrams illustrating a data sharesystem 1020 according to the second modified example. The differencebetween the configuration of the data share system 1020 of FIG. 19A andthe configuration of the data share system 1000 of FIG. 1A is that arelay apparatus 300 is connected to the data transmission path N as analternate device of an access point AP.

FIG. 19B illustrates a case where the data share system 1020 of thesecond modified example is used for a conference. In this case, theprocess of transmitting shared data among the data process apparatuses100 is performed by using the relay apparatus 300 instead of using theaccess apparatus AP as described above with FIG. 1B.

Hence, substantially the same effects (advantages) as those of the datashare system 1010 can be attained with the data share system 1020according to the first modified example. It is to be noted that wirelesscommunication, wired communication, or both may be used in thecommunication environment of the data share system 1020. Thus,communications may be performed in accordance with the type ofcommunication unit included in the relay apparatus 300.

Modified Example 3

Next, a modified example 3 (third modified example) of the presentinvention is described.

FIG. 20 is a schematic diagram illustrating a data share system 1030according to the third modified example. The difference between theconfiguration of the data share system 1030 of FIG. 20 and theconfiguration of the data share system 1000 of FIG. 1A is that differentnetwork areas Ea, Eb are connected to each other via a relay apparatus300. That is, in the third modified example, the relay apparatus 300relays (routing) data communications between the network area Ea and thenetwork area Eb. It is to be noted that the term “different networkareas” may be networks having a different segment(s).

FIG. 21 illustrates a case where the data share system 1030 of the thirdmodified example is used for a conference. In this case, the process oftransmitting shared data among the data process apparatuses 100 isperformed as follows. It is to be noted that, in the third modifiedexample, the document data shared by data process apparatuses 100 ₁-100₄ in the conference is retained (stored) in the data process apparatus100 ₁ connected to the network area Ea. Thus, in the third modifiedexample, the document data of the conference is shared between an officeA at which the network area Ea is built and an office B at which thenetwork area Eb is built.

First, the data process apparatus 100 ₁ of the organizer of theconference detects an access point APa located in a conference room ofthe office A and connects to the network area Ea. Thereby, the dataprocess apparatus 100 ₁ waits for other data process apparatuses 100₂-100 _(n) to transmit a participation notification to the data processapparatus 100 ₁.

In this state, the data process apparatus 100 ₂ of a participant Adetects the same access point APa and connects to the network area Ea.Thereby, the data process apparatus 100 ₂ notifies participation to theconference to the data process apparatus 100 ₁. Thereby, the dataprocess apparatus 100 ₁ notifies the device data of the data processapparatus 100 ₁ itself to the data process apparatus 100 ₂. Then, thedata process apparatus 100 ₂ obtains document data of the conferencefrom the data process apparatus 100 ₁ based on the device data notifiedto the data process apparatus 100 ₂. Thereby, document data can beshared.

Then, the data process apparatus 100 ₃ of a participant B detects thesame access point APa and connects to the network area Ea. Thereby, thedata process apparatus 100 ₃ notifies participation to the conference tothe data process apparatus 100 ₁. Thereby, the data process apparatus100 ₁ notifies the device data of the data process apparatus 100 ₂ whichhas obtained shared data to the data process apparatus 100 ₃. Then, thedata process apparatus 100 ₃ obtains document data of the conferencefrom the data process apparatus 100 ₂ based on the device data notifiedto the data process apparatus 100 ₃. Thereby, document data can beshared.

Then, the data process apparatus 100 ₄ of a participant C detects thesame access point APa and connects to the network area Ea. Thereby, thedata process apparatus 100 ₄ notifies participation to the conference tothe data process apparatus 100 ₁. Thereby, the data process apparatus100 ₁ notifies the device data of the data process apparatus 100 ₃ whichhas obtained shared data to the data process apparatus 100 ₄. Then, thedata process apparatus 100 ₄ obtains document data of the conferencefrom the data process apparatus 100 ₃ based on the device data notifiedto the data process apparatus 100 ₄. Thereby, document data can beshared.

Further, in a case where there is a new participant in the office B, thedata share system 1030 is used as follows.

The data process apparatus 100 ₅ of a participant D detects an accesspoint APb located in a conference room of the office B and connects tothe network area Eb. Thereby, the data process apparatus 100 ₅ notifiesparticipation to the conference to the data process apparatus 100 ₁ byway of the relay apparatus 300. Thereby, the data process apparatus 100₁ notifies the device data of the data process apparatus 100 ₁ itself tothe data process apparatus 100 ₅ by way of the relay apparatus 300.Then, the data process apparatus 100 ₅ obtains document data of theconference from the data process apparatus 100 ₁ based on the devicedata notified to the data process apparatus 100 ₅. Thereby, documentdata can be shared.

Then, the data process apparatus 100 ₆ of a participant E detects thesame access point APb and connects to the network area Eb. Thereby, thedata process apparatus 100 ₆ notifies participation to the conference tothe data process apparatus 100 ₁ by way of the relay apparatus 300.Thereby, the data process apparatus 100 ₁ notifies the device data ofthe data process apparatus 100 ₅ which has obtained shared data to thedata process apparatus 100 ₆ by way of the relay apparatus 300. Then,the data process apparatus 100 ₆ obtains document data of the conferencefrom the data process apparatus 100 ₅ based on the device data notifiedto the data process apparatus 100 ₆ by way of the relay apparatus 300.Thereby, document data can be shared.

Then, the data process apparatus 100 ₇ of a participant F detects thesame access point APb and connects to the network area Eb. Thereby, thedata process apparatus 100 ₇ notifies participation to the conference tothe data process apparatus 100 ₁ by way of the relay apparatus 300.Thereby, the data process apparatus 100 ₇ notifies the device data ofthe data process apparatus 100 ₆ which has obtained shared data to thedata process apparatus 100 ₇ by way of the relay apparatus 300. Then,the data process apparatus 100 ₇ obtains document data of the conferencefrom the data process apparatus 100 ₆ based on the device data notifiedto the data process apparatus 100 ₇ by way of the relay apparatus 300.Thereby, document data can be shared.

With the above-described configuration of the data share system 1030 ofthe third modified example, a distribution type data share service amongmultiple data process apparatuses 100 can be provided even betweendifferent network areas Ea, Eb. Accordingly, in a case where the relayapparatus 300 has a routing function (relay function) for relaying datacommunications between an external network (public area) and an internalnetwork (private area), the data share service can be provided in a widearea.

The data share function of the above-described embodiments can beperformed by causing a processor (e.g., CPU 106, 211) of the devicesconstituting the data share system 1000, 1020, 1030 (e.g., data processapparatus 100, projection apparatus 200) to execute the stepsillustrated above in, for example, FIGS. 7, 10, and 13 in accordancewith a program encoded with a programming language of a suitableoperating environment (platform).

For example, in a case of the data process apparatus 100, the programmay be recorded in the computer-readable recording medium 103 a.Thereby, the program can be installed in the data process apparatus 100via the drive device 103. Further, because the interface device 107 isincluded in the data process apparatus 100, the program may bedownloaded from a telecommunication line and installed in the dataprocess apparatus 100.

In the above-described embodiments, although the data processapparatuses 100 are managed based on the management identification datawhich are registered in the lists 20D, 30D, 40D and issued uponreception of the participation notification, the data processapparatuses 100 may be managed based on device identification data(e.g., IP address). In such case where the data process apparatuses 100are managed based on device identification data, only the deviceidentification data is registered in the lists 20D, 30D, 40D. In thiscase, the above-described participation order of the data processapparatuses 100 is determined based on, for example, the order in whichdevice identification data of the data process apparatus are registeredin the participant list 20D (listed order).

The present invention is not limited to the specifically disclosedembodiments, and variations and modifications may be made withoutdeparting from the scope of the present invention.

The present application is based on Japanese Priority Application Nos.2011-163381 and 2011-279510 filed on Jul. 26, 2011, and Dec. 21, 2011,respectively, the entire contents of which are hereby incorporatedherein by reference.

1. A data process apparatus for sharing shared data among a plurality ofdata process apparatuses participating in an event, the data processapparatus comprising: a participation notification reception unitconfigured to receive a participation notification from each of theplural data process apparatuses including first and second data processapparatuses in the event; and a notifying unit configured to notify thesecond data process apparatus to the first data process apparatus as adata obtain target from which the shared data is to be obtained; whereinthe second data process apparatus is a data process apparatus from whichthe participation notification has already been received by theparticipation notification reception unit.
 2. The data process apparatusas claimed in claim 1, wherein the notifying unit is configured todetermine the second data process apparatus as the data obtain targetbased on a data share status of the second data process apparatus and adata transmission status of the second data process apparatus, whereinthe determined second data process apparatus is notified as the dataobtain target to the first data process apparatus.
 3. The data processapparatus as claimed in claim 2, further comprising: a storage unitconfigured to store first and second lists therein, the first listincluding transmission completion data indicating one or more of theplural data process apparatuses that has completed transmission of theshared data, the second list including ongoing transmission dataindicating one or more of the plural data process apparatus that iscurrently transmitting or receiving the shared data; wherein thenotifying unit is configured to refer to the first and the second listsand identify at least one of the plural data process apparatuses, thatis not currently transmitting the shared data, from the second list,wherein the identified one of the plural data process apparatuses isdetermined as the data obtain target.
 4. The data process apparatus asclaimed in claim 3, wherein the notifying unit is configured todetermine the data process apparatus itself as the data obtain target ina case where the one of the plural data process apparatuses cannot beidentified from the second list.
 5. The data process apparatus asclaimed in claim 3, wherein in a case where the notifying unitidentifies more than one of the plural data process apparatuses, thenotifying unit is configured to identify the one of the plural dataprocess apparatuses according to an order in which the participationnotification is received by the participation notification receptionunit.
 6. The data process apparatus as claimed in claim 3, wherein thestorage unit is further configured to store a third list therein, thethird list indicating one or more of the plural data process apparatusesfrom which the participation notification is received, wherein the oneor more plural data process apparatus are indicated in the third list inan order in which the participation notification is received by theparticipation notification reception unit, wherein the notifying unit isconfigured to refer to the third list and identify the one of the pluraldata process apparatuses, that corresponds to a earliest receivedparticipation notification, from the third list.
 7. The data processapparatus as claimed in claim 3, further comprising: a transmissioncompletion reception unit configured to receive a transmissioncompletion notification the one or more of the plural data processapparatuses that has completed transmission of the shared data; whereintransmission completion reception unit is configured to update theongoing transmission data based on the received transmission completionnotification and register a new transmission completion datacorresponding to the transmission completion notification.
 8. The dataprocess apparatus as claimed in claim 6, wherein the participationnotification reception unit is configured to register the one or more ofthe plural data process apparatuses in the third list in the order inwhich the participation notification is received.
 9. The data processapparatus as claimed in claim 1, wherein the first data processapparatus includes a participation requesting device that requestsparticipation to the event organized by an organizer, wherein the seconddata process apparatus includes a participating device that isparticipating in the event, wherein the data process apparatus includesan organizer device of the organizer.
 10. A computer-readable recordingmedium on which a program is recorded for causing a computer of a dataprocess apparatus to execute a data sharing method for sharing shareddata among a plurality of data process apparatuses participating in anevent, the data sharing method comprising the steps of: receiving, bythe data process apparatus, a participation notification from each ofthe plural data process apparatuses including first and second dataprocess apparatuses in the event; and notifying the second data processapparatus to the first data process apparatus as a data obtain targetfrom which the shared data is to be obtained; wherein the second dataprocess apparatus is a data process apparatus from which theparticipation notification has already been received by the data processapparatus.
 11. A data share system for sharing shared data among aplurality of data process apparatuses participating in an event, thedata share system comprising: first, second, and third data processapparatuses; wherein the first data process apparatus includes aparticipation notification reception unit configured to receive aparticipation notification from each of the plural data processapparatuses including second and third data process apparatuses in theevent, and a notifying unit configured to notify the third data processapparatus to the second data process apparatus as a data obtain targetfrom which the shared data is to be obtained, wherein the third dataprocess apparatus is a data process apparatus from which theparticipation notification has already been received by theparticipation reception unit.